This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
Correct chef export usage message #859
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
`chef export`'s usage was incorrect. It stated a `client.rb` would be in the root of the export and includes the `-c client.rb` in the example. `export` creates a `.chef/config.rb` and can thus be invoked with the simpler `chef-client -z`. The message after the export command completes was correct. Now we correct it here too.
philoserf
changed the title
|
+1 |
1 similar comment
|
👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chef export's usage is incorrect. It states aclient.rbwill be in created in the root of the export and includes-c client.rbin the example.exportactually creates a.chef/config.rband can be invoked with the simplerchef-client -z.The message after the export command completes is correct. This PR corrects it here too.
Obvious fix.